System and method for automatically upgrading functionalities in a distributed network

ABSTRACT

The invention relates to a system and to a method for automatically providing system software which is filed in software packets, for system nodes which are arranged in a distributed network, in particular in a distributed automatic system. The inventive system comprises at least one system diagnosis tool which analyses the current state of the system of the distributed network and combines the current state of the data in system status data which is guided to at least one knowledge-based planning tool. Said knowledge-based planning tool produces a system plan for a novel system version, based on control and data, from the system status data and a planning data base, generating installation data for an automatic installation and configuration of the system configuration based on the produced system plan for the system nodes of the distributed network, and guides the installation data to at least one installation and configuration tool, provided in the system nodes. The installation and configuration tool, of the respective system node automatically selects, from the installation data, the software packets which are to be installed, installs and configures said latter, which enable, after configuring the installed software packets, the functionality of the distributed network to be re-established.

The invention relates to a system and a method for automaticallyupgrading system software stored in software packages, preferably froman installed version to a higher version, for system nodes arranged in adistributed network, in particular in a distributed automatic system.

BACKGROUND INFORMATION

The structure of a distributed network comprises a multiplicity ofsystem nodes which are interconnected via a network structure, forexample in a client-server relationship, and provide functionalitieswhich cannot be provided by means of an individual component. Operatorstations, engineering stations, archiving stations, control devices withprocessing stations, input and output units and communicationsinterfaces, for example, are used as system nodes in the distributednetwork.

The functional components are normally distributed among a multiplicityof system nodes, also referred to below as a computer or data processingdevice, which are interconnected via one or more physical networks.Operating systems, application programs, control programs and variousfunctional components of the system are installed on the system nodes,whereby the individual nodes with their various functional componentsare dependent on one another in different ways.

In order to upgrade the system software, which is stored in softwarepackages, a new or improved system version is installed on the computersof the distributed system, while retaining the user-specificapplications, such as, for example, project data and settings, wherebythe functional components of the existing system are replaced with newcomponents and the upgraded system is able to provide the same, albeitmodernized, fundamental functionality. This procedure is referred tobelow as a system upgrade.

Methods currently employed use, for example, installation programs,referred to as software installers, which perform the system upgrade ona single computer of the distributed system. Prior to the installationof the new programs, these installation programs check the existingsoftware configuration on the computer and, in the event of are-installation, suggest alternatives according to the available upgradefacilities of the software.

A detailed knowledge of the dependencies between the individual systemnodes is required in order to take into account the dependencies betweenthe individual system nodes of the distributed automatic system when thesoftware packages are upgraded.

Installation manuals often offer only a general knowledge of theexisting dependencies between the distributed system software. Theplanning of the system upgrade and the identification of the existingsystem components which need to be replaced with upgraded new componentsmust be carried out manually by the user.

Comprehensive expert knowledge is required to install the new softwarepackages on the various system nodes and configure the relationships anddependencies between the system nodes, since the procedure forinstalling and configuring the software packages is often onlyinadequately described and is difficult to follow in the guidelines andinstructions prescribed for that purpose.

Even existing analysis tools consider only compatibilities of individualsoftware packages and their versions with one another on one computer,but not logical system-related dependencies, such as, for example, inrelation to computer-independent software packages.

No dependency rules can be formulated for planning an automatic upgradefor all system nodes of the distributed system.

Newer versions of the complete system software are normally offered in aplurality of software packages, which the user himself must identify inorder to ascertain which system components need to be upgraded andinstalled on which nodes, or which system components need to be replacedwith a new version.

The system structure plans and the identification of the systemcomponents for a complete and correct installation of theinterrelationships and interdependencies of the system components arealso manually created and checked separately for each system component,whereby the administrative effort involved in upgrading the softwarepackages is highly time-consuming and increases in proportion to thescope of the system topology.

An automatic installation, configuration and system diagnosis of thedistributed system with an upgraded, newer version of the systemsoftware of the distributed automatic system over an existing versioncannot be carried out with the methods currently employed.

SUMMARY

The object of the invention is therefore to indicate a system forautomatically upgrading the functionalities stored in software packages,in particular in operating systems, application programs, controlprograms and/or various functional components of the system, for systemnodes arranged in a distributed network, in particular in a distributedautomatic system, whereby the aforementioned disadvantages are avoided.

This object is achieved according to the invention by a system with thefeatures indicated in claim 1. Advantageous designs, improvements of thesystem according to the invention and a corresponding method forimplementing a system of this type are indicated in further claims andin the description.

According to the invention, the system for automatically upgradingfunctionalities stored in software packages, also referred to below assystem software, for system nodes arranged in a distributed network, inparticular in a distributed automatic system, comprises a systemdiagnosis tool which analyzes the current system status of thedistributed network by iterating system diagnosis functions of thesystem diagnosis tool via the individual system nodes in the distributedsystem and by analyzing them for existing system components of thesystem nodes. By means of an analysis tool provided in the systemdiagnosis tool, the system functions supported by the currentlyinstalled automatic system and the system structure are first identified(e.g. the number of operator stations and servers present in the systemand the manner in which these are interlinked). This ensures thatprecisely this system with its characteristics is restored in the newersystem version following the upgrade. To do this, the analysis toolidentifies the software and hardware which is installed on eachindividual system node of the distributed network. To do this, theanalysis tool iterates via the individual system nodes and identifiesthe existing software and/or hardware.

In order to upgrade the functionalities of the automatic system, thesystem diagnosis tool collects the system-related data of thedistributed automatic system via the system nodes, for example by meansof the analysis tool, and summarizes the collected data in the systemstatus file. The system information collected in this way forms thebasis for the implementation of the system upgrade by means of aknowledge-based planning tool.

The knowledge-based planning tool automatically creates a system planfor a new system version from the system status file and a planningdatabase, in which general installation rules and system dependenciesare stored, by mapping the system components of the system nodes of theinstalled system onto the corresponding components of the new systemversion.

To do this, the planning tool resolves logical dependencies between thesystem nodes and functionalities of the distributed automatic system andbetween the requirements of the new system version and thus ensures inan advantageous manner that, following the definition of the new systemversion, only valid system plans are generated with the correct systemcomponents for the respective functionality to be supported, distributedamong the individual system nodes. Thus, for example, a software packageof a system node of the distributed automatic system in the new versioncan also be installed on further nodes. It is optionally provided forthese nodes in the new version that a further software package which wasnot yet available in an earlier version can additionally be installed.Higher performance requirements for the hardware of the individualsystem nodes are also provided when the system file is created.

The planning tool generates installation files for automaticinstallation and configuration of the system upgrade on the basis of thecreated system plan for the system nodes of the distributed network.

To do this, the planning tool is preferably stored in a separateplanning computer and, from the system components of the upgradedversion, automatically constructs a complete system configuration whichmatches the configuration of the installed system and has the samesystem functionalities. The planning database stored in the planningtool for this purpose comprises a model of a new system version withplanning rules, system dependencies, for example interdependencies ofthe software packages, system information, such as, for example,definitions of the system node types, possible configurationcombinations of the system components minimum and maximum system limitinformation, such as, for example, definitions of the maximum number ofoperator stations, system installation requirements and systemconfiguration steps.

The planning tool operates on the planning database, comprising theplanning and the underlying planning data, together forming aknowledge-based system.

The installation files preferably comprise information relating to thenode type and the name of each system node, the required operatingsystem, requirements for external basic software, additional hardwarerequirements, a compilation of software packages to be installeddepending on the respective system node and/or configuration data of thesystem nodes.

The created installation files are in each case forwarded to aninstallation and configuration tool present in the system nodes, whichautomatically selects from the installation files, installs andconfigures the software packages to be installed.

Following the configuration of the installed software packages, thefunctionality and the system characteristics of the distributed networkare advantageously restored in a more up-to-date system version, inparticular

-   -   the type and number of operator stations and/or engineering        stations,    -   the ability to communicate with connected control devices with        the number of connection stations,    -   supported redundancies of system nodes,    -   selected combinations of client/server structures on the same        system node,    -   installations of selected system applications,    -   the type and number of application servers,    -   the number of domain servers or, alternatively, the selection of        a workgroup and/or the domain names, i.e. the organizational        unit for administering the servers in the distributed network        and/or the network characteristics and/or the division of the        network into a plurality of subnetworks and/or network        redundancies,    -   the name and the identification addresses of the individual        system nodes,    -   created user and access rights of the domain and the automatic        system,    -   the system names and/or further user-specific system        configurations.

Following successful automatic installation of the software packages inthe system nodes of the distributed system, the system nodes areautomatically configured and the previously backed up application dataof the automatic system or the technical installation can then bereloaded onto the new system.

In an alternative design variant, the configuration of the softwarepackages can also be carried out in a user-controlled manner.

A further design variant of the invention is based on the principle thatthe analysis tool determines necessary extensions and/or adaptations ofthe hardware of the system nodes of the distributed system. To do this,the analysis tool reads in the corresponding generated installationfiles from the planning tool, compares these with the current hardwareand generates, for example, a report on hardware that is to beadditionally installed.

In a further advantageous design of the invention, the analysis tool isprovided in order to automatically carry out a check and/or verificationof the functionality of the distributed network and/or generate a systemstatus report.

The method with which the object is furthermore achieved is described inclaim 12. Here, the current system status of the distributed network isanalyzed by means of a system diagnosis tool and summarized in a systemstatus file. The system status file is forwarded to a knowledge-basedplanning tool, preferably installed on a planning computer.

According to the invention, a system plan for a new system version iscreated from the system status file and a planning database by means ofthe knowledge-based planning tool.

Installation files for automatic installation and configuration of thesystem upgrade are generated on the basis of the created system plan forthe system nodes of the distributed network and the installation filesare in each case forwarded to an installation and configuration toolpresent in the system nodes.

New software packages to be installed with the corresponding systemsoftware are automatically selected from the installation files,installed and configured by means of the installation and configurationtool of the respective system node, so that the functionality of thedistributed network is restored following the configuration of theinstalled software packages.

The procedure for installing and configuring a more up-to-date versionof the system software of a distributed automatic system over anexisting version is carried out in an advantageous manner with themethod according to the invention. The method automates the installationof the new system software and optionally comprises an automatic systemdiagnosis of the existing automatic system. The system diagnosisanalyzes the individual system nodes for system functionalities alreadyinstalled and from this generates a status report on the entire network.

The method described thus enables automatic restoration of thedistributed system with its functionalities in a newer version.

In an advantageous manner, no expert knowledge is required for theautomatic installation and configuration of the more up-to-date versionof the system software, since the installation and configuration of thesystem software are carried out automatically for all system nodes ofthe distributed network.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention and advantageous designs and improvements of the inventionare explained in detail and described with reference to the exampleembodiment shown in FIGS. 1 to 3, in which:

FIG. 1 shows a design form of the system according to the invention forautomatically upgrading system software stored in software packages fora system node arranged in an automatic system,

FIG. 2 shows an example of the procedure for automatically upgradingsystem software stored in software packages for system nodes arranged inan automatic system, and

FIG. 3 shows the procedure for automatically upgrading and/or extendingsystem software stored in software packages in an example of a networkstructure.

DETAILED DESCRIPTION

FIG. 1 shows an example of a design form of the system according to theinvention for automatically upgrading system software stored in softwarepackages for a system node SK arranged in an automatic system, wherebythe system nodes SK are, for example, operator stations, engineeringstations, archiving stations and controllers with processing stations,input and output units and communications interfaces. Only one systemnode SK is shown as an example in FIG. 1.

The system software integrated in the software packages comprises, inparticular, operating systems, application programs, control programsand/or functional components of the automatic system.

A system diagnosis tool 10 is stored in each case in the system nodes SKof the system according to the invention for automatically upgradingsystem software stored in software packages for a distributed automaticsystem. The system diagnosis tool 10 analyzes the current system statusof the automatic system by collecting the system-related data of theautomatic system by means of an analysis tool via the system nodes SK ofthe distributed network, and by collating a system status file 11 fromthe current system status. The system status file 11 is forwarded to aknowledge-based planning tool 20, which is arranged in a separateplanning computer.

The system diagnosis tool 10 analyzes the individual system nodes forsystem functionalities already installed and from this generates astatus report 12 on the current overall system. The status report 12 onthe current system status, which is contained in the system status file,records the functionalities that are present in the currently installedsystem. The planning tool 20 requires this information in order toidentify the functionalities that need to be upgraded.

The knowledge-based planning tool 20 creates a system plan 21 for a newsystem version from the system status file 11 and a planning database23. The system plan 21 may optionally be output or displayed, forexample in the form of a report on the planned upgrade.

On the basis of the created system plan 21 for the system nodes SK ofthe distributed automatic system, the planning tool 20 generatesinstallation files 22 for automatic installation and configuration ofthe system upgrade for the system nodes SK of the distributed system.

The generated installation files 22 are forwarded in each case to aninstallation and configuration tool 50, 60 present in the system nodesSK, which automatically selects from the installation files 22, installsand configures the software packages to be installed and restores thefunctionality of the entire automatic system.

In an advantageous design of the invention, the analysis tool 70automatically performs a verification of the functionality of theautomatic system on the individual system nodes. With this finalverification, the successful restoration of all functionalities in thenew system version is concluded.

To do this, the analysis tool 70, which has already previously collectedthe system-related data of the automatic system via the system nodes SKof the distributed network, checks the completeness of the performedsystem extension of the system software of all system nodes and createsa status report 71 with the information on the system software upgradeand the upgraded system status of the distributed system. This report 71forms, for example, as a system pass, the basis for future serviceactivities and upgrades on the automatic system.

Before the new system software is set up, the hardware of the individualsystem nodes SK must often be adapted to the requirements of the newversion.

The analysis tool 70 is thus also provided to ascertain, from theplanning tool 20, necessary extensions and/or adaptations of thehardware of the respective system nodes SK of the distributed system bymeans of the generated installation files 22.

The analysis tool 70 alerts the user automatically to any new hardwarerequirements of the individual system nodes SK which have not been met.To do this, the analysis tool reads in the corresponding generatedinstallation files 22 from the planning computer PR, and compares thefiles 22 with the currently installed hardware. The ascertained hardwareextensions are output or indicated, for example, in the form of a report30 on additional hardware requirements.

For the installation and configuration of the operating system andnetwork, the generated installation files 22 receive individual scriptsfor each system node SK for the automatic installation and configurationof the operating system and network. This automatically ensures, forexample, that the correct operating system is pre-installed on theindividual servers or clients of the system. Further scripts set, forexample, the names of the system nodes SK and identification addressesof the system nodes, and add them to the corresponding system domain.The scripts are automatically activated here by a tool 40.

FIG. 2 shows an example of the procedure for automatically upgradingsystem software stored in software packages for system nodes arranged inan automatic system.

The method according to the invention describes a number of steps withwhich the software packages are automatically upgraded for eachindividual system node SK and all information required in order torestore the system functionality is compiled in a newer version in aplurality of the installation files 22. The installation files 22 areused as input for the subsequent steps of the method and an individualset of defined node-specific files is generated for each node.

In a first step 1, the system-related data are collected by the analysistool 70 via all system nodes SK in the distributed network. To do this,the analysis tool 70 iterates via the individual nodes SK and determinesthe hardware present therein, for example the performance of the centralunit (CPU), or the memory capacity of the system nodes SK, the installedsystem software, the software from third-party providers, such as theoperating system, the configurations of the system nodes SK, such as,for example, the identification address, the node name, the user accessset-up and software configurations. The individual nodes are analyzedremotely from a central planning computer PR of the automatic system,which collates the results of the analysis and summarizes them in asystem status file 11.

In a second step 2, a new, still empty, system plan 21 is first createdby means of the planning tool 20 on the basis of a model of the newsystem version to which the installed system is to be upgraded. Theplanning computer 20 then reads in the system status file 11 generatedby the analysis tool 70 and maps the individual system components of theinstalled system onto the corresponding components of the new version.To do this, the planning tool 20 consults the individual systemcomponents of the installed version in a mapping table from theunderlying planning database and determines the installationrequirements and rules for each system component in the new version. Foreach system component, the mapping table thus identifies which softwarepackages of the new version are to be installed in which sequence onwhich nodes, which configuration steps are to be performed, whichadditional hardware requirements exist for the system nodes SK, and onwhat the new system component is to be installed. The planning tool 20successively fills the empty model of the newly created system plan 21with the identified system components of the new version, until theresulting plan finally represents a complete functional mapping of thestill installed system onto the new system version.

The configuration data of the still installed system are thentransferred by means of the planning tool 20 into the new system plan21, whereby the configuration data comprise, for example, thedesignations of the system nodes of the originally installed system,settings of the identical identification addresses, transfers of useraccess and user rights into the new system.

In an alternative design variant, a specific system version can also beselected from a selection of different possible versions onto which theexisting system is to be upgraded via a graphical user interface (GUI)of the planning tool 20 provided in the planning tool 20.

Before the new system software can be set up, the hardware of theindividual system nodes SK may need to be adapted according to therequirements of the new version. Thus, in a third step 3, the adaptationof the hardware of the system nodes SK is prepared in that the user isautomatically alerted by the analysis tool 70 to any new hardwarerequirements of the individual system nodes SK which may not have beenmet. To do this, the analysis tool 70 reads in the correspondinggenerated installation files 22 from the planning tool 20 andautomatically compares these with the current hardware, whereby thesystem node SK computers can of course only be upgraded manually.

For the installation and configuration of the operating system and thenetwork, individual scripts are allocated in a fourth step 4 to thegenerated installation files 22 for each system node SK for theautomatic installation and configuration of the operating system and thenetwork. Thus, it is automatically ensured, for example, that thecorrect operating system is pre-installed on the individual servers orclients of the system. The scripts are automatically activated here by atool 40.

The installation of the new system version of the software components onthe individual system nodes SK is carried out in a fifth step 5 in sucha way that the list of new software packages to be installed is obtainedfor each system node SK by means of an installation tool 50 from theinstallation files 22, which are supplied, for example, by aninstallation CD, and these software packages are installed according tothe predefined sequence on the relevant node SK. The originallyinstalled system software packages of the individual system nodes SK arereplaced by means of the installation tool 40 with the new softwareversion, so that the functionality of the entire automatic system iscompletely restored in the new version.

In a further step 6, the configuration of the software components in thesystem nodes SK in the new system is carried out by means of aconfiguration tool 60.

The system software of the upgraded system nodes SK is thusautomatically configured following its installation and the previouslybacked up application data of the automatic system are reloaded into thenewly installed and/or extended system software.

In a final step 7, a concluding verification of the successfulrestoration of all functionalities in the new system version is carriedout. To do this, the completeness of the performed steps 1 to 6 ischecked by means of the analysis tool and a new system status report 71is generated with the details of the completed system upgrade and thenew system status. The system status report 71 is used, for example, asa system pass for future service activities on the distributed automaticsystem, in particular for further upgrades.

FIG. 3 shows the procedure for automatically upgrading system softwarestored in software packages in an example of a distributed networkstructure. The example of a network structure comprises the networks Aand B with a multiplicity of system nodes SK and the dependenciesbetween the system nodes SK and the control devices SG connected tothem.

For upgrading the system software stored in the software packages over aplurality of system nodes SK of the distributed network, observing thelogical structure of all the distributed system components, generaldependencies and rules for the upgrade 100 of the entire distributedsystem described in FIGS. 1 and 2 are formulated in the planningdatabase 23, also referred to as the rule database, of the planning tool20, are administered and automatically checked during the upgrade 100 inthe system nodes of the.

The method for the automatic system upgrade 100 maps newer systemsoftware S5 onto system software S4 on the basis of the rule database 23and, with reference to the rules and system dependencies stored in therule database 23, identifies the adaptations which need to be carriedout in the system nodes SK in order to restore a distributed networkready for operation with, as far as possible, the same functionality inthe newer version S5.

The invention claimed is:
 1. A system for automatically upgrading systemsoftware stored, on a non-transitory computer readable medium, insoftware packages for system nodes arranged in a distributed automaticsystem of a network, comprising: at least one system diagnosis tool, foranalyzing a current system status of the distributed automatic system,summarizing the current system status in a system status file byrecording for each system node at least current hardware and softwareinstalled therein, and for forwarding the system status file to at leastone knowledge-based planning tool, wherein a system plan is stored in aseparate planning computer, the knowledge-based planning tool forcreating a rule-based and data-based system plan for a new systemversion from at least the installed hardware and software recorded inthe system status file and a planning database, the knowledge-basedplanning tool being configured to create the system plan for the newsystem version being based on a model of the new system version in whichthe system status file is used to populate the model of the new systemby mapping each system node to a system component of the new systemversion, generating installation files, a sequence for installing theinstallation files, and identifying configuration steps to be performedfor the installed files for automatic installation and configuration ofa system upgrade on the basis of the system plan for each system node ofthe distributed automatic system, and forwarding the installation filesin each case to at least one installation and configuration tool presentin each system node, the installation and configuration tool of eachsystem node being configured for automatically selecting from theinstallation files, installing and configuring software packages to beinstalled, and restoring the functionality of the distributed automaticsystem following the configuration of the installed software packages.2. The system as claimed in claim 1, wherein the system softwareintegrated into the software packages comprises functional components.3. The system as claimed in claim 1, wherein the system diagnosis toolcollects system-related data via the system nodes of the distributedautomatic system in order to record the current system status by ananalysis tool and summarizes said data in the system status file.
 4. Thesystem as claimed in claim 3, wherein the analysis tool automaticallycarries out at least one of a verification of the functionality of thedistributed automatic system and a generation of a status report withinformation relating to the upgrading of the system software of thedistributed automatic system.
 5. The system as claimed in claim 3,wherein the analysis tool determines at least one of extensions andadaptations of the hardware of the system nodes of the distributedautomatic system.
 6. The system as claimed in claim 1, wherein theplanning database comprises a model of a new system version with atleast one of planning rules, system dependencies, system node types,system limit information, system installation requirements, and systemconfiguration steps.
 7. The system as claimed in claim 1, wherein thesystem diagnosis tool and the installation and configuration tool arearranged in the system nodes of the distributed automatic system.
 8. Thesystem as claimed in claim 1, wherein the installation files compriseinformation relating to at least one of node type and name of eachsystem node, an operating system, requirements for external basicsoftware, additional hardware requirements, a compilation of thesoftware packages to be installed depending on the respective systemnode, and configuration data of the system nodes.
 9. The system asclaimed in claim 1, wherein, following the configuration of theinstalled software packages, at least one of system characteristics andfunctionalities of the distributed automatic system including at leastone of a type and number of operator stations and engineering stations,an ability to communicate with connected control devices with a numberof connection stations, supported redundancies of system nodes, selectedcombinations of client and server structures on the same system node,installations of selected system applications, a type and number ofapplication servers, a number of domain servers or, alternatively, atleast one of a selection of at least one of a workgroup and a domainname, at least one of the network characteristics, a division of thenetwork into at least one of a plurality of subnetworks and networkredundancies, a name and identification addresses of individual systemnodes, created user and access rights of the domain and the automaticsystem, system names, and further user-specific system configurationsare restored.
 10. The system as claimed in claim 1, wherein theconfiguration of the installed software packages can be carried out in auser-controlled manner.
 11. A method for automatically upgrading systemsoftware stored in software packages for system nodes arranged in adistributed automatic system, comprising: analyzing a current systemstatus of the distributed automated system by means of a systemdiagnosis tool, which summarizes a current system in a system statusfile by recording for each system node at least current hardware andsoftware installed therein, and forwarding the system status file to aknowledge-based planning tool, wherein planning is stored in a separateplanning computer, creating a rule-based and data-based system plan fora new system version from the installed hardware and software recordedin the system status file and a planning database by means of theknowledge-based planning tool, the system plan for the new systemversion being created based on a model of the new system version inwhich the system status file is used to populate the model of the newsystem by mapping each system node to a system component of the newsystem version, generating installation files, a sequence for installingthe installation files, and identifying configuration steps to beperformed for the installed files for automatic installation andconfiguration of the system upgrade at each system node of thedistributed automatic system on the basis of the created system plan,forwarding the installation files in each case to an installation andconfiguration tool present at each system node, automatically selecting,installing, and configuring software packages in the installation filesby means of the installation and configuration tool of each system node,and restoring the distributed automatic system following theconfiguration of the installed software packages.
 12. The method asclaimed in claim 11, wherein functional components are stored in thesoftware packages.
 13. The method as claimed in claim 11, whereinsystem-related data are collected via the system nodes of thedistributed automatic system by means of an analysis tool integratedinto the system diagnosis tool in order to record the current systemstatus and are summarized in the system status file.
 14. The method asclaimed in claim 13, wherein at least one of a verification of thefunctionality of the distributed automatic system is automaticallycarried out by means of the analysis tool and a status report isgenerated with information relating to the upgrading of the systemsoftware of the distributed automatic system.
 15. The method as claimedin claim 13, wherein at least one of necessary extensions andadaptations of the hardware of the system nodes of the distributedsystem are determined by means of the analysis tool.
 16. The method asclaimed in claim 11, wherein the model of a new system version with atleast one of planning rules, interdependencies of the software packages,definitions of the system node types, configuration combinations, andsystem restrictions is formed as the planning database.
 17. The methodas claimed in claim 11, wherein the system diagnosis tool and theinstallation and configuration tool are arranged in the system nodes ofthe distributed automatic system.
 18. The method as claimed in claim 11,wherein at least one of information relating to the node type and thename of each system node, an operating system, requirements for externalbasic software, additional hardware requirements, a compilation of thesoftware packages to be installed depending on the respective systemnode, and configuration data of the system nodes is stored in theinstallation files.
 19. The method as claimed in claim 11, wherein,following the configuration of the installed software packages, systemcharacteristics and functionalities of the distributed automatic system,including at least one of a type and number of operator stations andengineering stations, an ability to communicate with connected controldevices with the number of connection stations, supported redundanciesof system nodes, selected combinations of at least one of client andserver structures on the same system node, installations of selectedsystem applications, a type and number of application servers, a numberof domain servers or, alternatively, at least one of a selection of aworkgroup and a domain name, at least one of network characteristics, adivision of the network into a plurality of subnetworks, and networkredundancies, a name and identification addresses of individual systemnodes, created user and access rights of the domain and the automaticsystem, system names and further user-specific system configurations arerestored.
 20. The method as claimed in claim 11, wherein theconfiguration of the installed software packages is carried out in auser-controlled manner.
 21. The system as claimed in claim 2, whereinthe functional components are at least one of application programs andcontrol programs of the distributed network.
 22. The method as claimedin claim 12, wherein the functional components are at least one ofoperating systems, application programs and control programs of thedistributed network.
 23. The system as claimed in claim 1, wherein theanalysis tool is configured to determine whether hardware requirementsof the new system version are met by the current hardware installed ateach respective system node.
 24. The system as claimed in claim 23,wherein the analysis tool is configured to alert a user of new hardwarerequirements based on the determination.
 25. The method as claimed inclaim 11, comprising: determining whether hardware requirements of thenew system version are met by the current hardware installed at eachrespective system node.
 26. The method as claimed in claim 25,comprising: alerting a user at a respective system node of new hardwarerequirements based on the determination.
 27. The system as claimed inclaim 1, wherein the knowledge-based planning tool is configured tocreate the system plan based on a logical structure of distributedsystem components in the model, which includes dependencies between thesystem nodes and control devices connected thereto.
 28. The method asclaimed in claim 11, wherein creating the system plan is based on alogical structure of distributed system components in the model, whichincludes dependencies between the system nodes and control devicesconnected thereto.